I have created an inbound sync rule in the FIM portal to import groups from an external system (SQL Server) into the metaverse. I can import the rule from the FIM MA into the FIM connector space but when I run a full sync on the FIM MA I get the error "sync-rule-inbound-flow-rules-invalid". The only way I have found around the error is to remove all the attributes from Inbound Attribute Flow in the sync rule. However, this defeats the purpose of having the sync rule in the first place. Searching the Web, I have come across posts from other people with "sync-rule-inbound-flow-rules-invalid" problems but the solutions do not seem to work in my situation. A little background about the sync rule Metaverse Resource Type: group External System Resource type: group Relationship Criteria: accountName (metaverse) = "string field" (ConnectedSystemObject) Create resource in FIM: yes Inbound attribute flow: - Domain - Member - DisplayName - accountName - MembershipLocked - MembershipAddWorkFlow - Type - Scope I am new to FIM so it's possible I have overlooked something in the setup of this sync rule. Any suggestions on possible causes of this issue would greatly appreciated.

Did u use functions in attribute flow? Can u give more details on the inbound attribute flows and Scoping filter? Jessie Song

There is no scope filter. In regards to the attribute flows, no functions are used. Here is further information about the attribute flows Set up of Inbound attribute flow for the inbound Synchronization Rule. Metaverse External System (SQL Server View) - Domain Domain (string) - Member Member (multi value attribute) - DisplayName ObjectDescription (string) - accountName ObjectID (string) - MembershipLocked 'false' (set up as a string literal) - MembershipAddWorkFlow 'Owner Approval' (set up as a string literal) - Type 'Security' (set up as a string literal) - Scope 'Universal' (set up as a string literal) Is this the info you were asking for? If not, please clarify what details you are looking for in regards to the sync rule.

So if you just include any one flow rule from the above list, you get the error? I would verify if you are getting error with complete list or any flow rule causes this. Glenn Zuckerman, Microsoft Identity Technologies

I deleted all the MAs and recreated them. The FIMMA export now works. I believe the issue was related to metaverse schema objects I had created (ADUser and ADGroup), which I used initially then later abandoned. Deleting the MAs, deleting the metaverse schema additions and then recreating the MAs seemed to fix the original issue.